Methods for point of use medication control

ABSTRACT

Methods for controlling the dispensing of medication are provided. The method can include holding at least one medication within a dispenser and alerting a patient that a dose of medication is to be taken or an optional dose of medication is available to be taken. Once the patient is present for receiving a does of medication, the identification of the patient can be confirmed. Upon confirmation of the identification, a dose of medication for the patient can then be dispensed and removal of medication from dispenser can be confirmed. The method can also include providing a location determination device with the dispenser to permit locating the dispenser.

RELATED APPLICATION

This application is a continuation of and claims priority to co-pendingU.S. patent application Ser. No. 12/953,754 filed Nov. 24, 2010 which isa divisional of and claims priority benefits to U.S. patent applicationSer. No. 11/649,471 filed Jan. 4, 2007, now U.S. Pat. No. 7,885,725which claims the benefit of U.S. Provisional Patent Application Ser. No.60/756,372, filed Jan. 5, 2006, the entire contents of which are bothhereby incorporated by reference herein.

TECHNICAL FIELD

The subject matter described herein relates generally to systems andmethods for medication compliance. More particular, the subject matterdisclosed herein relates to devices, systems and methods for dispensingmedication to an intended patient at predetermined and appropriate timesin an outpatient setting to increase the likelihood of proper medicationmanagement of a patient after leaving the direct care of a doctor orhealth provider/professional.

BACKGROUND

The rate of compliance with medication regimens in outpatient settingsis generally regarded as poor. Even under the watchful eye of doctors,studies have shown that trained professionals working in a controlledsetting make significant errors in the delivery of medication topatients. Compliance with such medication regimens have been shown to beworse after the patient leaves the hospital and the medicationmanagement is required to be performed by the patient or some otheruntrained family member. For example, studies have shown that patientsdirected to take a single medication once per day have only succeededabout 70% of the time. Studies have further shown that, when three dosesper day are required, compliance with such medication regimens falls toabout 50%. Further, such studies show that compliance and compliancefailures for such medication regimens do not correlate with social,economic, or educational variables.

Failure to comply with medication regimens prescribed by doctors canhave severe consequences. For example, in the outpatient setting, apatient's recovery can be slowed and progress toward recovery can beminimized by the patient's failure to follow the prescribed medicationregimen provided by a trained professional. Such lack of compliance canhelp in the development of drug resistant strains of bacteria andviruses. For example, tuberculosis has developed certain drug resistantstrains in Africa due to the fact that rural patients have begun lengthymedication regimens that required multiple doses but fail to followthrough and complete these regimens. Thereby, the tuberculosis has beenallowed to persist in a form that has become resistant to the treatmentbeing used. Such drug resistance strains could be minimized if thepatients were able to properly follow through with their medicationregimens.

A further concern applies to certain classes of medication that areprone to abuse. For example, certain narcotics and anxiety reducingmedications are known to be addictive. For such medications, a patientwill often begin to take increasing amounts of the medication at morefrequent intervals that do not comply with the prescribed regimen setforth for the use of the drug. The controlling of dosing for thesemedications in the outpatient setting is so notoriously difficult thatmany physicians have simply begun to refuse to prescribe them.

Concerns about the diversion of a medication from the patient to otherindividuals have reduced the outpatient prescription of such drugs. Forexample, medications such as Oxycontin have addictive qualities and alsohave street value as a recreational drug. Often, people who areprescribed such a drug end up selling it to users who consume itrecreationally. This concern is so great for Oxycontin that some statelegislatures have considered banning its use.

In the examples provided above, drugs that were once valuable to societyhave lost part of their effectiveness through their misuse in one way oranother. Therefore, in light of the above, a need exists for a systemthat allows outpatient medication to be dispensed in a secured,controlled, and monitored fashion to more effectively manage andorganize the care given to a patient.

SUMMARY

In accordance with this disclosure, novel devices, systems and methodsfor point-of-use medication control in outpatient settings are provided.

The present disclosure provides devices, systems and methods forpoint-of-use medication control that can employ single dose distributionand dispensing at predetermined and appropriate times through patientawareness and identification as well as through compliance confirmation.This and other purposes as may become apparent from the presentdisclosure can be achieved, in whole or in part, by the presentlydisclosed subject matter when taken in connection with the accompanyingdrawings as best described herein below.

BRIEF DESCRIPTION OF THE DRAWINGS

A full and enabling disclosure of the present subject matter includingthe best mode thereof to one of ordinary skill in the art is set forthmore particularly in the remainder of the specification, includingreferences to the accompanying Figures in which:

FIG. 1 illustrates a schematic of an embodiment of a system for apoint-of-use medication control according to the present subject matter;

FIG. 2 illustrates a schematic of an embodiment of a dispenser deviceused within the system according to FIG. 1;

FIGS. 3A-3C illustrate perspective views of components of an embodimentof a system for a point-of-use medication control according to thepresent subject matter;

FIG. 4 illustrates a backside perspective view of a component of theembodiment of the system for a point-of-use medication control accordingto FIGS. 3A-3C;

FIGS. 5A-5E illustrate interactive screen display windows used for userinteraction with a controller of an embodiment of a system for apoint-of-use medication control according to the present subject matter;

FIG. 6 illustrates a schematic representation of embodiments of possibledata tables used within a database of an embodiment of a system for apoint-of-use medication control according to the present subject matter;

FIG. 7 illustrates a schematic representation of interactions betweenthe data tables of FIG. 6;

FIG. 8 illustrates a screen of a database that employs the data tablesof FIG. 6;

FIG. 9 illustrates a screen of a database that employs the data tablesof FIG. 6;

FIG. 10 illustrates a screen of a database that employs the data tablesof FIG. 6;

FIG. 11 illustrates a screen of a database that employs the data tablesof FIG. 6;

FIG. 12 illustrates a screen of a database that employs the data tablesof FIG. 6;

FIG. 13 illustrates a screen of a database that employs the data tablesof FIG. 6;

FIG. 14 illustrates an interactive screen display window used for aninternet web browser interface for a database of an embodiment of asystem for a point-of-use medication control according to the presentsubject matter;

FIG. 15 illustrates an interactive screen display window used for aninternet web browser interface for a database of an embodiment of asystem for a point-of-use medication control according to the presentsubject matter;

FIG. 16 illustrates an interactive screen display window used for aninternet web browser interface for a database of an embodiment of asystem for a point-of-use medication control according to the presentsubject matter;

FIG. 17 illustrates an interactive screen display window used for aninternet web browser interface for a database of an embodiment of asystem for a point-of-use medication control according to the presentsubject matter;

FIG. 18 illustrates an interactive screen display window used for aninternet web browser interface for a database of an embodiment of asystem for a point-of-use medication control according to the presentsubject matter;

FIG. 19 illustrates an interactive screen display window used for aninternet web browser interface for a database of an embodiment of asystem for a point-of-use medication control according to the presentsubject matter;

FIG. 20 illustrates an interactive screen display window used for aninternet web browser interface for a database of an embodiment of asystem for a point-of-use medication control according to the presentsubject matter;

FIG. 21 illustrates an interactive screen display window used for aninternet web browser interface for a database of an embodiment of asystem for a point-of-use medication control according to the presentsubject matter;

FIG. 22 illustrates an interactive screen display window used for aninternet web browser interface for a database of an embodiment of asystem for a point-of-use medication control according to the presentsubject matter; and

FIG. 23 illustrates an interactive screen display window used for aninternet web browser interface for a database of an embodiment of asystem for a point-of-use medication control according to the presentsubject matter.

DETAILED DESCRIPTION

Reference will now be made in detail to presently preferred embodimentsof the present subject matter, one or more examples of which are shownin the Figures. Each example is provided to explain the subject matterand not as a limitation. In fact, features illustrated or described aspart of one embodiment can be used in another embodiment to yield stillanother embodiment. It is intended that the present subject matter coversuch modifications and variations.

FIG. 1 illustrates a medication dispensation control system, generallydesignated as 10. System 10 includes a dispenser, generally designatedas 20, that is capable of holding and delivering at least one dose ofmedication to a patient in an outpatient setting. Dispenser 20 can havean outer housing 22 that encloses the operational components of aportion of system 10 within dispenser 20 and prevents tampering andunauthorized removal of medication from dispenser 20. In use, dispenser20 could be used to distribute units of medications in the form oftablets, pills or capsules at predetermined times to specified andidentified individuals.

System 10 can also include a controller, generally designated as 30.Dispenser housing 22 can enclose controller 30, which is operablyconnected to operable components of dispenser 20. Controller 30 canautomatically operate dispenser 20 to provide a dose of medication tothe patient at the appropriate or predetermined time. For example,controller 30 can be programmable with a medication dispensing programwhich includes a data store comprising the predetermined time to operatedispenser 20 and the name of the at least one medication. The data storeof the medication dispensing program can also comprise patient data anda patient compliance schedule. Patient data can include the first andlast name of the patient, the age of the patient, medical historyinformation, or the like. Biometric information, such as fingerprintdata or the like can also be considered patient data.

The data store of the medication dispensing program on controller 30 canalso comprise caregiver data. The caregiver can be anyone such as afamily member or nurse who is charged with taking care of the patient.In such cases where a caregiver is necessary to administer themedication to the patient, the caregiver can be allowed to engage system10 to receive the medication to be administered to the patient.Caregiver data can include first and last name of the caregiver, contactinformation of the caregiver, or the like. Biometric information, suchas fingerprint data or the like can also be considered caregiver data.Through such information, the caregiver can gain access to themedication to be administered to the patient.

The data store of the medication dispensing program on controller 30 canalso comprise compliance notification data. Compliance notification datacan include the frequency of timely compliance by the patient, data onthe dates and times at which compliance occurs, or the like. The datastore of the medication dispensing program on controller 30 can furthercomprise pharmacy data, physician data, insurance data and emergencycontact data.

Controller 30 can include devices that emit any suitable type of signalto indicate dispenser 20 is ready to provide a dose of medication forthe patient to receive. For example, a display screen, such as aninteractive user interface display screen 32 can be provided that canalert the patient that a dose of medication is ready to be dispensed. Inthe embodiment shown in FIG. 1, a simple display saying that thedispenser is ready to dispense is shown on display screen 32. Thedisplay also shows a user interface 34 on display screen 32 with whichthe patient can interact to acknowledge receipt of the signal. The userinterface 34 can be a response button 36 in the form of a graphicdisplay button that the user activates by touching the screen at thedisplay location of the graphic display button. By activating thisbutton 36, the patient acknowledges receipt of the signal and thedispensing can begin. Other response mechanisms can be providedincluding other graphic display buttons. For example, button 38 can beprovided that allows the patient to skip the dispensing of the dose ofmedication.

Besides the display 32, a speaker 40 can be provided to provide anaudible signal that would be emitted by the speaker 40. Speaker 40 canbe internally contained with outer housing 22 or it can be external. Inthis manner, a patient who cannot view display 32 can still be notifiedof the availability of the dose medication. Once the patient hasacknowledged receipt then the audible signal can end as well. Otherresponse mechanisms can be provided to allow the user to acknowledgereceipt of the signal that medication is available for dispensing. Forexample, a physical button can be provided that the patient canactivate. Further, a lever or switch can be provided that can beactivated by the patient after receipt of the signal.

To monitor and verify that the dispensing of the drug is to the correctindividual, an identification verification device, generally designatedas 50, can be provided in outer housing 22 of dispenser 20 and can beconnected to controller 30. Identification verification device 50 can beused to verify that the patient for whom the medication is to be givenis present and ready for distribution of the medication. In this manner,identification verification device 50 can be used to verify the identityof the patient.

The identification verification device 50 can be a biometricidentification device. For example, TruePrint technology basedfingerprint sensors offered by AuthenTec, Inc. of Melbourne, Fla., canbe used as the fingerprint system 52. Fingerprint system 52 can includea touch screen 54 that can provide a place for the patient to place afinger. Fingerprint system 52 can then read the fingerprint and compareit to stored data to confirm that the individual trying to receive thedoses of medication is in fact the intended recipient.

Other identification verification devices such as retina scans, userpasswords, voice recognition or the like can be used to verify theidentity of the patient before distribution of the dose of medicationwithin dispenser 20.

System 10 can further include a communication device 60 that can also bein operable communication with controller 30. Communication device 60can be a wireless communication device. Such an electronic communicationdevice 60 that operate on a wireless platform and can include an antenna62 that transmits signals through a cellular network 64 to a remotefacility, or location 70 that can house a database 72 for use incontrolling dispenser 20. Database 72 can be accessed by the patient'sdoctor, pharmacy, and/or administrator of the medication system, as wellas the patient. Through the wireless connection provided by cellularnetwork 64, controller 30 can communicate through an Internet ServiceProvider 66 with the database 72 at the remote facility 70. InternetService Provider 66 manages data collection and distribution to and fromdatabase 72 for the users. The users can include the patient, thepatient's doctor and/or pharmacist, and/or the administrator of themedication system.

Through the Internet 68, appropriate individuals can gain access to theinformation provided to and from dispenser 20 to monitor and control thedosing of the medication. For example, such individuals or locations caninclude the patient, the doctor's office, the pharmacy, or theadministration facility, where administrator resides. Authorizedpersonnel from the doctor's office can gain access to patient anddispenser information stored on database 72 through a clinician browser74. Authorized personnel from the pharmacy can gain access to patientprescription information stored on database 72 through a pharmacistbrowser 76. Authorized personnel from the administration facility cangain access to clinician, pharmacist, and dispenser information storedon database 72 through an administrator browser 78. Data stored caninclude information such as predetermined times to operate dispenser 20.The data can also include the name of the medication being distributed,the patient's data, the patient's compliance schedule, caregiver data,and compliance notification data as well as pharmacy data, physiciandata, insurance data, and emergency contact data. Further, suchinformation can be provided on a data store connected to controller 30within dispenser 20 itself.

Controller 30 can be programmable to connect to a predetermined InternetService Provider 66 through electronic communication device 60 andcellular network 64 in order to transmit the patient's data and obtain apatient registration. Controller 30 can also be programmable to connectto Internet Service Provider 66 through electronic communication device60 in order to transmit the compliance schedule and compliancenotification data from database 72. Controller 30 can also beprogrammable to connect to Internet Service Provider 66 throughcommunication device 60 in order to transmit or receive the pharmacydata, physician data, insurance data, and emergency contact data.

When controller 30 has received instruction that the signal has beenreceived, controller 30 can transmit a compliance notification toInternet Service Provider 66 to be sent on to the physician, pharmacist,or administrator. Alternatively, the compliance notification can be sentto database 72 where the physician, pharmacist or administrator canaccess the notice of compliance. Similarly, if the recipient does notacknowledge the signal and the signal goes on for a predetermined time,controller 30 can send a signal to Internet Service Provider 66 totransmit a non-compliance notification that then can be forwarded ontothe physician, pharmacist, or administrator as well as stored in thedatabase as needed.

The user can use display screen 32 to communicate with controller 30 toorder a refill of the medication or to order a new dispenser 20containing the medication when the system is connected to thepredetermined Internet Service Provider 66. In this manner, the user cantake dispenser 20 back to the pharmacy to have it refilled or to pick upa new dispenser 20 which can be taken back and used by the patient. Theinterchangeable dispensers 20 provide a way to easily monitor the drugsthat are placed into each dispenser 20 by the pharmacist. The pharmacistcan ensure that the correct information is downloaded into controller 30within the appropriate dispenser 20 for the appropriate patient beforethe patient picks that dispenser 20 up from the pharmacy or doctor'soffice.

Controller 30 can also be programmable to update and transmit thecaregiver data and compliance notification data to the database orInternet Service Provider 66 and/or the clinician browser 74, pharmacistbrowser 76, or administrator browser 78 when the system is connected toInternet Service Provider 66. Controller 30 can automatically connectand send such information as needed or desired. Further, communicationdevice 60 can receive notices from the predetermined Internet ServiceProvider 66 when the system is connected to the predetermined InternetService Provider 66. Controller 30 can be programmable to receive anduse notices as necessary to better manage dispenser 20. Similarly,controller 30 can be programmable to access and search databasesprovided by Internet Service Provider 66.

System 10 can also include a location determination device (notspecifically shown) such as an integrated global positioning system(“GPS”) receiver that can be contained within outer housing 22 ofdispenser 20. For example, a location determination device can beintegrated into controller 30. Such a device permits the whereabouts ofdispenser 20 to be easily determined. If someone tries to stealdispenser 20 or dispenser 20 is misplaced, the patient can contact theadministrator who can track down the location of dispenser 20. Forexample, the administrator can use tracking software and communicationsystems of a GPS system used within dispenser 20 for determining thelocation of that dispenser 20. In this manner, theft of the dispensercan be minimized, and, hopefully, the chances of the perpetrator beingcaught and prosecuted can be increased.

System 10 can also include a telephone modem within dispenser 20 thatallows it to be hooked up to a telephone line to call for emergencyassistance, if needed. Dispenser 20 can include an emergency assistancebutton 24 that can be actuated to cause controller 30 to dial anemergency telephone number. Dispenser 20 can also include a dispensingdoor 26 which can be used to permit access into dispenser 20 to remove adose of medication. Dispenser 20 can also include a microphone 42 toallow for the patient to communicate with an emergency facility, whichis contacted by controller 30.

Dispenser 20 can further include a lockout for disabling functionalityof the system based upon predetermined criteria. Such a lockout can bein furtherance to identification verification device 50, which can alsobe used to prevent unwanted access to the medication contained indispenser 20. However, the lockout can help to prevent overdosing of thepatient or dosing of the patient when the patient is not in a conditionto receive such medication. For example, the lockout can include abreath sensor 46 for determining a breath alcohol level. The breathalcohol level can then be compared to predetermined criteria that caninclude a maximum breath alcohol level that would be allowable fordispensing of the dose of medication from dispenser 20. The lockout canalso include an interactive cognitive test on predetermined criteriathat can include a minimum cognitive level based on the results of thetest to allow dispensation of the dose of medication from dispenser 20.The interactive cognitive test can be performed through a display on theinteractive display screen 32. In this manner, overdosing can beprevented as well as dosing of a patient who is too heavily medicated ordisoriented to take the medication. Health hazards relating to themixing of medications or alcohol with medications can be prevented.Based on the results from the lockout, an emergency contact, thedoctor's office, pharmacy or a caregiver of the patient can be alertedthat the patient is in a state that requires attention.

FIG. 2 illustrates a schematic internal view of the dispenser 20.Dispenser 20 includes a pill magazine 100 which can be filled at apharmacy through a fill door 102. Fill door 102 can be locked to preventaccess to the store of pills 104 within pill magazine 100. A tamperswitch 106 can also be provided to monitor and record the opening offill door 102 or other tampering that can occur to fill door 102 oncedispenser 20 has left the pharmacy.

Pill magazine 100 can be defined by an inner wall 108 and an outer wall110 and two side walls. Further, a slanting base surface wall 112 canextend within the dispenser 20 from the outer wall 110 downward to abottom wall 110B forming an angle α with bottom wall 110B. Inner wall108 does not extend to base surface wall 112, thereby leaving an openingfor pills to slide downward into a dispensing well 114.

Outer wall 110 and/or bottom wall 110B can be internal walls that residewithin outer housing 22 (shown in FIG. 1). Alternatively, outer wall 110and/or bottom wall 110B can be external walls which help to form outerhousing 22 of dispenser 20.

At a filling location such as a pharmacy, when fill door 102 is openedand pills 104 are placed into pill magazine 100, pills 104 flow downwardunder gravitational force to the base surface wall 112 and slide downits sloped surface which slopes downward from external wall 110 at angleα. The pills 104 can slide into dispensing well 114 underneath end 116of inner wall 108. A dispensing well wall 118 extends upward andparallel to inner wall 108 of pill magazine 100 to help define anopening in dispensing well 114. Dispensing well wall 118 permits only asmall number of the pills from pill magazine 100 fill the dispensingwell 114 at any given time.

Dispensing well wall 118 can also include a slanted base wall 120 thatslopes upward from the base surface wall 112 of pill magazine 100. Avibrator 122 can be used and positioned below base surface wall 112 toadd vibration to base surface wall 112, thereby agitating pills residingon base surface wall 112. This vibration can cause pills 104 to fall ormove down the sloped surface of the base surface wall into dispensingwell 114. Vibrator 122 can be in communication with an optical detector124 which can be placed along dispensing well wall 118 or base surfacewall 120. Optical detector 124 can detect whether any pills reside indispensing well 114. If optical sensor 124 does not detect the presenceof pills 104 within dispensing well 114 then vibrator 122 can beactivated to cause any pills residing in pill magazine 100 to slide downthe slope surface of base surface wall 112. Optical detector 124 can beany conventional optical sensor known in the art.

Once it is determined that pills 104 reside in dispensing well 114, avacuum pick up 126 can be actuated to pickup a pill 104 for delivery todispensing door 26 of dispenser 20. The opening of dispensing well 114can be opened and closed by motorized shutter 128, which can provide aslanted surface 130. When motorized shutter 128 is in a closed positionas shown in FIG. 2, pills 104 within pill magazine 100 and dispensingwell 114 are prevented from removal from dispenser 20.

A tilt sensor 132 can be provided which is activated when dispenser 20is tilted to prevent its operation while inverted or shaken. Tilt sensor132 can be in communication with controller 30 (see FIG. 1). Suchinformation as whether dispenser 20 is shaken or tilted can be sent fromtilt sensor 132 to controller 30. Controller 30 can then renderdispenser 20 inoperable and it can also forward a message to InternetService Provider 66 and onto the clinician browser 74, pharmacistbrowser 76, or administrator browser 78 (see FIG. 1). Tilt sensor 132can be a conventional equilibrium sensor. Tilt sensor 132 can also beconfigured to shut down dispensing operations directly if tilting orshaking is detected.

Dispenser 20 also can include, as noted above, a vacuum pickup 126,which can be a part of a vacuum mechanism 134 for removal of at leastone pill from dispensing well 114 for delivery to dispensing door 26 ofdispenser 20. Vacuum mechanism 134 can include a vacuum pump 136 thatcreates a negative pressure that can be used to pick up a pill 104 fromdispensing well 114. Vacuum mechanism 134 can also include a vacuum tube138 that is connected to vacuum pump 136 on one end 140 such that thenegative pressure created within vacuum pump 136 creates a vacuumthrough vacuum tube 138. Vacuum pickup 126 can be secured on the otherend 142 of vacuum tube 138. Vacuum pickup 126 as well as vacuum tube 138can be extended into dispensing well 114 to retrieve a pill therefrom.

Vacuum pickup 126 can include a vacuum cup 144 disposed at its enddistal from vacuum tube 138. Vacuum pickup 126 can be raised and loweredby a step motor 146. In the embodiment shown, step motor 146 can rotatea belt 148 which is secured to the vacuum pickup 126. By running stepmotor 146 in one direction, vacuum pickup 126 is lowered. By runningstep motor 146 in a reverse direction, the rotation of belt 148 can bereversed and vacuum pickup 126 can be raised.

A vacuum sensor 150 can be in communication with vacuum mechanism 134.Vacuum sensor 150 can detect whether or not a pill is stuck to thevacuum pickup 126 at vacuum cup 144 thereof. In this manner, vacuummechanism 134 determines when a pill is secured to vacuum pickup 126 sothat it can be raised from dispensing well 114 and ready for delivery todispensing door 26 of dispenser 20.

In operation, once the patient has acknowledged receipt of the signalindicating time for the receipt of a dose of medication and the patienthas identified himself or herself to system 10, dispenser 20 is ready todispense a dose of medication to the intended recipient. When a pill 104is to be dispensed, motorized shutter 128 can be moved from its closedposition as shown in FIG. 2 to an open position (see FIGS. 3A and 3B) toallow vacuum pickup 126 to be lowered into dispensing well 114. As notedabove, tilt sensor 132 can prevent shutter 128 from opening if dispenser20 is tilted, inverted or shaken.

Optical sensor 124 can check to determine if any pills 104 are inposition within dispensing well 114 to be picked up by vacuum pickup126. If no pills 104 have fallen into dispensing well 114, vibrator 122vibrates base surface wall 112 to agitate base surface wall 112 withinpill magazine 100 to cause any pills 104 within pill magazine 100 tofall down the sloped surface of base surface wall 112 into positionwithin dispensing well 114. As noted above, base surface wall 112 can beat an angle α as measured from the bottom outer wall 110B that providesenough of a slope to encourage pills 104 to slide into dispensing well114.

As vacuum pickup 126 is lowered, vacuum pump 136 creates negativepressure which creates a vacuum suction through vacuum cup 144 of thevacuum pickup 126. As vacuum cup 144 comes in contact with a pill andthereby seizes the pill through vacuum pressure, vacuum sensor 150detects that a pill is stuck to vacuum pickup 126. Step motor 146 canthen be run in reverse, such that vacuum pickup 126 is raised out ofdispensing well 114.

Optionally, an optical detector 152 can be secured to vacuum pickup 126to make sure a pill is in position for pickup. Optical detector 152optically determines if a pill resides within dispensing well 114 thatcan be picked up through vacuum pickup 126. If no pill is sensed by theoptical detector 152, then vibrator 122 can be run. Vacuum pickup 126can be lowered by step motor 146 by rotating belt 148 in a specifieddirection until optical detector 152 detects a pill at the pickup.Vacuum pump 136 starts creating a negative pressure that lifts the pillto vacuum cup 144. Vacuum sensor 150 then detects that a pill is stuckto vacuum pickup 126. If a pill is detected, vacuum pickup 126 is raisedby reversing step motor 146 so that belt 148 raises vacuum pickup 126.

Once vacuum pickup 126 with the pill attached to vacuum cup 144 hascleared dispensing well 114, motorized shutter 128 can then be movedinto a closed position of the opening in dispensing well 104 as shown inFIG. 2. At this point, the vacuum pump 136 shuts off, allowing the pillto fall against slanted surface 130 of shutter 128. The pill falls to aremoval position 154 at dispensing door 26 of dispenser 20. An opticalsensor 156 can be placed in proximity to removal position 154 to detectthat the pill is in place before allowing access to the pill throughdispensing door 26. If no pill is detected, then the steps of picking upa pill through vacuum pickup 126 can be repeated until it is recognizedthat a pill is in position for removal from dispensing door 26 ofdispenser 20. Vacuum pickup 126 can be recessed slightly into the bodyof dispenser 20 to ensure that the pill attached thereto drops freelywhen the vacuum is removed.

FIGS. 3A, 3B, and 3C illustrate components of an embodiment of a system10, including a dispenser 20 outside of its outer housing that can beused to enclose the dispenser 20 and the other components. Thecomponents are shown free standing relative to one another and can bearranged in any known manner that provides necessary access to anyinteractive component that the patient must engage to receive theintended doses of medication. Dispenser 20 can include pill magazine100, vacuum mechanism 134, and motorized shutter 128 as well asdispensing well 114. A controller 30 as well as an identificationverification device 50 can also be included as components of system 10.Further, a location determination device 80 can be included in system10. As noted above, location determination device 80 can be a GPS devicethat can easily be used to locate the whereabouts of the system 10.Controller 30 can be a microcomputer such as a personalized digitalassistant (“PDA”), for example, an Ipaq 3635. Controller 30 can also bea computer, programmable logic controller, or the like. Controller 30can operate using any compatible operating system. For example,controller 30 can operate using Microsoft Pocket PC. Controller 30 canprovide a display screen 32 which can be a touch-tone interactivedisplay. Further, controller 30 can provide physical buttons 36B whichcontrol a cursor on display screen 32 to allow interaction between thepatient-user and the controller 30.

Controller 30 can be in communication with identification verificationdevice 50 in the embodiment shown. Identification verification device 50can be a fingerprint reader 52 which has a touch screen 54 on which apatient-user can place a finger in order for the fingerprint reader 52to read the user's fingerprint.

Controller 30 can also be in communication with the vacuum pump 136 ofvacuum mechanism 134 as well as a step motor 160 that is used to controlshutter 128 for opening and closing of shutter 128 to provide accessthrough the opening in dispensing well 114. Further, controller 30 canbe in communication with step motor 162 (shown in FIG. 4) used to raiseand lower vacuum pick up 126 through a slide 170 to which vacuum cup 164is attached. Slide 170 rides within a slot 172 that extends downwardinto dispensing well 114. Vacuum sensor 150, which is used to determinethe presence of a pill on vacuum pump 164, also can be in communicationwith controller 30.

Vacuum mechanism 134 components can be controlled by a separate vacuumcontroller 166 as shown in FIGS. 3A-3C and 4 that is in communicationwith the controller 30. Such vacuum controller 166 can be a Parallaxmicrocontroller offered by Parallax, Inc., of Rocklin, Calif. Controller30 can direct operation of vacuum mechanism 134 by communicating withvacuum controller 166. In other embodiments, controller 30 can directlycontrol vacuum mechanism 134 and its components.

Location determination device 80 can be in communication with controller30 to pass location information to the controller 30 and onto a remotefacility 70 or Internet Service Provider 66 (See FIG. 1). Further,location determination device 80 can produce a signal that isindependent of controller 30 and communication device 60 that isdetectable by an appropriate positioning system such as a GPS. In suchembodiments, the signal from the location determination device 80 can bepicked up by the administrator as needed.

All components of system 10 can share a common battery power supply (notshown). All components of system 10 can also communicate with controller30 via an RS232 serial interface.

In operation, controller 30 can be preloaded and programmed withdispensing instructions as to the times of use at the location wheredispenser 20 is filled. Programming and fingerprint templatetransmission also can be done remotely. A patient's fingerprint wouldonly need to be enrolled once for use on multiple units.

Pill magazine 100 of dispenser 20 can store a single type of pill orcapsule therein. Pill magazine 100 can be filled at a pharmacy.Dispenser 20 can then be secured to prevent access to pill magazine 100or prevent unauthorized removal of the pill or capsule from dispenser20. As described, a fill door (not shown) can be used to fill pillmagazine 100. The fill door can then be locked and a tamper switch canbe used to detect any opening of the fill door.

Once controller 30 determines it is time to dispense medication to thepatient, a signal can be sent out to notify the patient that it is timeto receive a dose of medication. For example, a visual signal can beshown on display screen 32 to notify the patient of availability of thedose of medication. Additionally, or alternatively, an audible signalthrough a speaker system (not shown) can be sent out by controller 30 toalert the patient of the availability of a dose of medication. Thepatient can acknowledge receipt of the signal through use of buttons36B. Then, the patient can verify his or her identity throughidentification verification device 50. The patient can interact withsystem 10 via display screen 32 of controller 30, or through buttons 36Bof controller 30, to verify the cognitive level of the patient throughcognitive tests. Additionally, or alternatively, a breath analyzermechanism can be provided to discern the alcohol level within thebloodstream of the patient to ensure no ill effects of mixing themedication and alcohol will result from allowing dosage to be dispensedto the patient. Once identification has been verified and any cognitivetests which can be employed have been fulfilled, controller 30 caninstruct vacuum mechanism 134 to remove a pill or capsule fordistribution to the patient.

At such time, step motor 160 can drawn back shutter 128 such thatdispensing well 114 is opened to allow vacuum pick up 126 to enterdispensing well 114 to remove a pill or capsule disposed therein asshown in FIG. 3A. As discussed above, a tilt sensor can be disposedwithin the dispenser that identifies when the machine is titled,inverted, or shaken. In such instances, shutter 128 is placedimmediately into a closed position, if it is not already in thatposition, and dispenser 20 is rendered inoperable. Further, dispenserdoor 26 can be secured in a shut position to prevent removal of anypills, and controller 30 can send a signal to the appropriate locationsto notify doctors, pharmacist, or an administrator of the unauthorizeduse of dispenser 20.

Once shutter 128 is in an open position as shown in FIG. 3A, vacuum pickup 126 with its vacuum cup 164 can be inserted into the well through themotion of step motor 162. In the embodiment shown in FIG. 4, step motor162 operates a slide 170 in a conventional manner, so that slide 170 ismoveable along a slot 172. For example, slide 170 may be attached to abelt (not shown) that can be rotated in a forward or reverse directionby step motor 162. Slot 172 can run parallel to dispensing well 114 andcan extend above dispensing well 114 as shown in FIG. 4. Vacuum pickup126 (shown in FIGS. 3A-3C) can be secured to slide 170 such that vacuumcup 164 extends downward. Vacuum cup 164 can be a bellow type vacuumcup, which easily secures to a pill or capsule once placed under anegative pressure.

Once shutter 128 is moved to its open position through step motor 160,vacuum pickup is lowered by step motor 162 into dispensing well 114.Controller 30, or alternatively the vacuum controller 166 as shown inFIG. 4, can start vacuum pump 136 to create a negative pressure throughvacuum tube 138. This negative pressure creates a vacuum through vacuumcup 164 at the end of vacuum pickup 126. As shown in FIG. 3B, step motor162 lowers vacuum pickup 126 into dispensing well 114 such that vacuumcup 164 comes in contact with a pill or capsule. The negative pressurecreated by vacuum pump 136 pulls the pill or capsule against vacuum cup164 such that the pill or capsule is held by vacuum cup 164 for removalfrom dispensing well 114. Controller 30, or vacuum controller 166,verify by vacuum sensor 150 that vacuum cup 164 has picked up a pill orcapsule. At this point, controller 30, or vacuum controller 166, willthen instruct step motor 162 to raise vacuum pickup 126 out ofdispensing well 114. Vacuum sensor 150 will continue to monitor toensure that a pill or capsule is secured by vacuum cup 164. Once thestep motor 162 has raised vacuum pickup 126 to a predetermined pointabove dispensing well 114, controller 30, or vacuum controller 166, willinstruct step motor 162 to close shutter 128 as shown in FIG. 3C.

Once vacuum pickup 126 with a pill or capsule attached to vacuum cup 164is raised above dispensing well 114, shutter 128 can be closed.Controller 30, or vacuum controller 166, can turn off vacuum pump 136.Thereby, the negative pressure is removed from the vacuum pickup 126 andvacuum cup 164 allows the pill or capsule secured thereto to drop ontoslanted surface 130 of shutter 128. Slanted surface 130 feeds the pillor capsule into the chute and down to removal position 154 in front ofdispenser door 26 as shown in FIG. 2. At this point, the pill or capsuleis ready for removal from dispenser 20 by the patient or caregiver.

Once the patient has used a fingerprint touch sensor 52 to confirmidentity and the proper number of pills or capsules are dispensed andremoved, controller 30 records the removal of the pills. Afterdispensing medication on timed intervals, controller 30 can activate acellular modem 174 of a communication device 60 and connect to acomputer server to exchange data with the Internet Service Providerserver and the database that contains tables for patients, pharmacistsand dispensing units. For example, information can be exchanged twice aday. Further, information can be provided to the patient's doctor,pharmacist and the administrator of the outpatient medication system. Inthis manner, data can be exchanged between controller 30 and thecomputer which provides access to other necessary parties including thepatient through the cellular modem 174 and antennae 176 of theelectronic communication device 60, both of which are in communicationwith controller 30. For example, dose history can be sent to the serverin this manner. Further, if the dispenser is reported as lost, theserver can communicate with the dispenser, while the locationdetermination device 80 can be used to identify the location of thedispenser. Once the location is determined, coordinates are then relayedto the server so the dispenser can be located and recovered.

Software running on the database server 72 (see FIG. 1) can include anSQL database to store information about dispensation, enrolled patients,prescription, and doctors (clinicians). This data is served out todispensers as described above and also to authorize users via Internet68 using a web browser based interface as discussed below.

For embodiments which use a graphical user interface that is displayedon the display screen 32 of the controller 30, the user interfacerequires very little input from the patient. As shown in FIG. 5A, adispensing window 180 shows a cell 182 for the next medication dose anda countdown timer cell 184 for that dose. The top dispense button 186provides a button to dispense the regularly scheduled medication dose.However, the regularly schedule dose can be dispensed through othermechanisms such as by verifying the identity of the patient through anidentification verification device. The change dose button 180 is notfor use by the patient but is used by the doctor, pharmacist and/or theadministrator of the out-patient medication system. Such a change dosebutton 188 is code locked.

Extra doses which can be provided for certain ailments such asmigraines, anxiety, and pain medications, can be handled by the bottomhalf of the window 180. A countdown timer cell 190 shows when an extradose is or will be available. The second dispenser button 192 activatesthe dosing cycle. The quit button 194 can be provided to end thedispensing program.

A dosing window 200 illustrated in FIG. 5 is provided for pharmacyaccess to medication directions. The window 200 is code locked toprevent access by unauthorized users. The window 200 can be accessedthrough the dispensing window 180 after the correct access code has beenentered. Ideally, only the pharmacy has the correct code to unlock andgain access to the dosing window 200 as shown in FIG. 5B. The dosingwindow 200 includes dosing cells 202 that provide the time identifier204 for each dose as well as amount identifier 206 for each dose. Inthis manner, scheduling time for each dose can be set by the pharmacistbefore dispenser 20 leaves the pharmacy. Approval button 208 is providedto approve the dosing schedule provided in dosing cells 202 once ascheduled time and dosage has been entered. A cancel button 210 permitscanceling of the dosing schedule provided in dosing cells 202. In theembodiment shown, eight dosing cells 202 are provided, but not all ofthese cells 202 need to be used. For example, only four doses can benecessary within a 24 hour period. Thus, only four sets of dosing cellswill need to be used. Further, if necessary, more dosing cells 202 canbe provided.

A change lock code button 212 can be provided to change the lock codeneeded to gain access to the dosing window by the pharmacist. Dosingwindow 200 does not have to be used by the pharmacist. The controller ofthe system can be easily programmed via internet access to the centraldatabase which then can be communicated to the controller containedwithin the dispenser in the care of the patient. In the event that theinternet access is unavailable, dosing window 200 allows programmingaccess to authorized individuals.

FIG. 5C illustrates dosing ready window 214 that alerts the patient thatthe medication is ready to be taken. As noted above in regards to thedose ready window shown on screen 32 of FIG. 1, the alert can includethe activation of a signal light, tone, vibration, or voice prompt,thereby providing both visual and audio signals to alert the patientthat a dose is ready. The dose ready window 214 can include a message216 which alerts the patient to the fact that a dose is ready. Further,the dose ready window 214 can include an acknowledgement button 218 thatcan be activated to acknowledge receipt of the signal and thereby promptthe user to engage the finger sensor for activation of the dispenser toprovide a dose of the medication.

Once the signal screen shown in FIG. 5C is acknowledged through touchingof the acknowledgement button 218, a fingerprint reading window 220 asshown in FIG. 5D can be displayed on display 32 to prompt the patient totouch a fingerprint sensor for positive identification of the patientbefore dispensing of the dose of medication. The fingerprint sensorprovides rapid, reliable, and easy use and demands very little of thepatient. Use of this identification verification device verifies thatthe patient is present at the time the medication is made available. Thesensors on the system further check to see that the dose is picked up.While the system does not guarantee that the medication goes from handto mouth of the patient, it can eliminate every barrier except willfulrefusal. If the patient is having trouble then a trouble button 222 canbe provided that serves to trigger a transmission to a central databasethat technical support is needed. If finger reading proves to be apersistent problem, the use of the fingerprint reader can be bypassed.

Further, the display window can provide a graphical user interface forchanging the lock code as shown in FIG. 5E. A change lock code window224 provides the ability of the pharmacist to change the lock code toprevent unauthorized access to the dosing window which can be used toalter the dosing schedule and amounts of the dosing of the medication.Change lock code window 224 can include cells to enter the old code atcell 226, enter a new code at the new code cell 228 and confirm the newcode at confirmation cell 230. Once the new code is typed into both thenew code cell 228 and the confirmation cell 230, a change code button232 can be activated to change the lock code. Thereby, the old code canbe changed to a new code that controls the access to the dosing window200. If the code typed into the new code cell 228 and confirmation code230 do not match, the new code must be re-entered in both cells 228,230. If the pharmacist does not wish to change the code, a cancel button234 is provided to close the change code lock window 224.

A server can be used to store a database program that can include thecentral database 72 as shown in FIG. 1. For example, an Apple G5 serveravailable from Apple Computer, Inc., of Cupertino, Calif., can run OpenBase 9.0, an SQL database program, available from OpenBaseInternational, Ltd., of Concord, N.H., that can comprise the centraldatabase. An example of a structure of database 72 is shown in FIGS.6-13. In particular, an array table database structure is described,although it is to be understood that other common forms of databases canbe used. Further, different data can be collected, stored and usedwithin the Database 72 other than the specific examples shown in FIGS.6-13. FIGS. 6-13 are screen shots of a user interface for the database.Database 72 holds and distributes information on the doctors, patients,prescriptions, pharmacist, and dispenser units. Within the screen shotsof FIGS. 6-13, different verbiage and words can be used to describe thesame item. For example, dispensers can be called “trackers” within thescreen shots of the particular embodiment of the database. Also, doctorsand/or pharmacist can be identified by the term “Clinicians.” The datainterconnections can be shown within the Figures. The data fields ofeach table are also listed. Fields can be added or removed as needed.These changes are dynamically added to the web interface.

As shown in FIG. 6, an array table can be provided for the clinician,patient, script, tracker, and EO_PK_table. These array tables containdifferent interconnected information. A clinician table 236 can includefields for the row ID, time stamp, version, clinician ID, the first nameand last name of the clinician and patient ID. Similarly, a patienttable 238 can have the fields for the row ID, time stamp, version,clinician ID, the first name and last name of the patient and patientID. A script table 240 can include fields for row ID, time stamp,version, length of time in days, dose amount, the interval betweendoses, the medication, the script ID, the strength level of themedication, and tracker ID for each dispenser. Script table 240 caninclude information that would appear on a prescription or prescriptionbottle. A tracker table 242 corresponds to the information about thedispenser used by the patient. The fields of the tracker table 242include row ID, time stamp, version, contact time, patient ID, pillsremaining, script ID, tracker ID for each dispenser, and tracker numberfor each dispenser. Also, the fields within the tracker table can alsoinclude longitude and latitude of the dispenser provided by a locationdetermination device, such as a GPS device, within the dispenser as wellas the position time also provided by the location determination devicewithin the dispenser.

The EO_PK_table 244 includes a row ID, time stamp, version, name, andprimary key information. The EO_PK_Table is a database programming tableused in setting up enterprise objects and primary keys within thedatabase. The EO_PK_Table can be used to verify access to different dataand is used to assign primary key attributes to the data entered andaids in placement within the right tables. The EO_PK_Table isautomatically generated by the database software. The EO_PK_Table maynot be necessary depending on the database software and structure used.

FIG. 7 shows the shared data fields and relationships between thedifferent tables. For example, information is shared between cliniciantable 236 and patient table 238. Patient table 238 also sharesinformation with tracker table 240 which in turn shares information withscript table 242. In this manner, when certain information is updatedwithin one of the tables, this information can be passed on to otherassociated tables. FIG. 8 shows a screen shot of an upper level screenwhich identifies the different tables by class names and names. FIGS. 9and 10 show screen shots of data view information. In particular, FIG. 9illustrates a clinician table identifying the clinician by theclinician's ID and his or her first and last name. FIG. 10 illustratesthe top most level of the database.

FIG. 11 shows a patient table which identifies the patient by his or herfirst and last name in the fourth column and patient ID in the fifthcolumn. The patient table provides a column for clinician ID to identifythe clinician for each patient. Each row contains specific informationfor the patient within that row and assigns each patient a patient IDnumber displayed in column 6.

FIG. 12 shows a script table which identifies the number of days forwhich the medicine in each row is to be taken and the amount of the doseto be given as well as the interval measured in hours between doses. Thescript table also provides the name of the medication being administeredand the strength of the medication. The script ID is provided as well asthe tracker ID which is used to administer and dispense the associatedmedication at the appropriate doses and intervals. The Script table canalso include information on each dose scheduled to be taken within a 24hour period instead of relying just on the interval information. Thiswould allow for greater dosing flexibility. Information regarding theamount of time that a dose will be available after it is due can beprovided in the Script table. Further, lock out times can be providedthat set the minimum time between doses. For example, if the lock outtime is set at one hour and an optional dose is taken, then the nextdose would not be available until after an hour of taking that optionaldose. Information can also be provided as to the number of tablets orcapsules dispense for each dose or optional dose requested. Also, thetime interval between optional doses can be provided in the Scripttable.

FIG. 13 illustrates a tracker table which identifies the row ID andcontact time. The contact time provided is the last time the dispenserhad contact with the database to exchange information. The tracker tableshows the longitude and latitude of each tracker whose information iscontained within the data field. The tracker table also provides columnsfor the patient ID for the patient and the number of pills remaining.The position time in which the position of each dispenser was lastcommunicated to the database is also provided. The Script ID links thedispenser to its prescription. Tracker ID for each dispenser as well asa tracker number and script ID are provided within the tracker table foreach dispenser. The tracker table can include other information,including dose history that can have a text summary of the times andstatus of each dose. The dose history of optional doses can be includedas well. Further, information as to the time of the last dose dispensingand time of the last optional dose dispensing can also be included inthe Tracker table or other tables.

As stated above, different database structures can be used withdifferent information being provided. For example, database structuressuch as hierarchical models, network models, relational models, objectmodels, relational-object models, or the like, can be used. Further,while database 72 is shown at a remote facility, database 72 can also bestore on the memory of the controller of the system, if the controllerhas a large enough capacity.

The clinicians in the form of doctors and/or pharmacist, as well as themedication system administrator can have access to various tables withinthe database. Further, the patient can have limited access to certaininformation contained within the database. The clinicians, doctors,pharmacist, administrators and patients can have access to the databasethrough an internet web browser interface as previously discussed. Thebrowser based web interface can be provided by an Apple G 5 server or inthe Apache web server with web objects acting on the application server.Such internet web browser interfaces essentially make the centraldatabase accessible to users and to controllers on the dispensersthrough the internet.

FIGS. 14 through 23 illustrate embodiments of screen shots which a userwould encounter through an internet web browser interface. Inparticular, the screen shots illustrate screens that would be seen by anadministrative level user progressing through the database. FIG. 14illustrates a login screen which requires the input of a user name andpassword. An assistant box can be checked in order to identify theperson logging into the system as an assistant. Once the user name andpassword have been entered, the user can click on the login button. Thislogin screen provides a secure access to the data to authorizedindividuals.

FIG. 15 shows a next level screen that provides access to the differentdata tables to the administrator user. In particular, FIG. 15 shows aweb search page that can be accessed from any web browser. For example,the administrator user can gain access to the clinician table, thepatient table, the script table, or the tracker table from this page.The administrator user can look up specific data by using the scrollmechanism provided to look up the different fields within each datatable. For example, the user can look up information by last name forthe clinician or patient by entering in the specific last name for theclinician or the patient on which the user is trying to retrieveinformation. Further, the user may be able to find information withinthe script table. For example, the user can look up information in thefield for medication within the script table. Another example can be tolook up information within the tracker table related to a certaintracker number by entering the tracker number within the space providedin the cell for the tracker table. Each field within each differenttable can be searched in this manner. The scroll button beside the fieldenter cell allows the user to scroll through the different fields.Further, the relationship of what you are trying to search can also bechanged. Instead of having information pulled up for the clinician'slast name, the “equal sign” can be changed to a “not equal sign”,thereby pulling up information on every clinician that does not have thespecified last name. In this manner, a variety of ways of searching thedifferent tables within the database can be accomplished through the webbrowser.

Once in the data table, links can be followed to other related tables.At each level, data editing is possible. Different levels of access areprovided for each type of user. Doctors can only see their own patientslisted. Similarly, pharmacies would only see information on theircustomers listed. Doctors would be allowed to modify their own patientsdosing schedule but no add patients or prescriptions. Similarly,pharmacies would be able to add prescriptions but not modify them. Ifdispensing units are distributed from a central location, onlyadministrators would need to add patients, clinicians, or dispensers tothe database. Privileges to add or modify data entries could be assignedto fit individuals. FIGS. 16 through 23 illustrate different informationthat could be edited within the different tables by an administrativeuser.

No screen for controller to server communications is illustrated sincethese communications occur using machine-to-machine protocols. Simpleobject access protocol (“SOAP”) calls are used to exchange XML packetsbetween the dispensers and the database server. Contacts are initiatedby the controllers of the dispensers when needed or at timed intervals.The controllers transmit their status of the dispensers and can acceptnew programming or data (including fingerprint templates for new users).As is evident from the screen shot of the dispensers (trackers data) inFIG. 21, position information is also transmitted. This would allowrecovery of lost or stolen units.

The embodiments of the present disclosure shown in the drawings anddescribed above are exemplary of numerous embodiments that can be madewithin the scope of the following claims. It is contemplated that theconfigurations for the devices, systems and methods for point of usemedication control in the out-patient setting can comprise numerousconfigurations other then those specifically disclosed. Thus, it isintended that the scope of the patent issuing herefrom will only belimited by the scope of the pending claims.

What is claimed is:
 1. A method for controlling dispensing ofmedication, the method comprising: (a) holding at least one medicationwithin a dispenser device; (b) alerting a patient that a dose ofmedication is to be taken or an optional dose of medication is availableto be taken; (c) confirming identification of the patient through abiometric identification device; (d) dispensing a dose of medication forthe patient from the dispenser device; (e) confirming removal ofmedication from the dispenser device; and (f) providing a locationdetermination device with the dispenser device to permit locating thedispenser device.
 2. The method according to claim 1, further comprisinglocating the dispenser device via the location determination device uponnotification of misplacement of the dispenser device.
 3. The methodaccording to claim 1, further comprising communicating informationbetween the dispenser device and a remote location about dispensing ofthe medication.
 4. The method according to claim 3, wherein the remotelocation comprises a central data store and communicating informationbetween the dispenser device and the remote location comprises reportingstatus of the dispenser device to the central data store.
 5. The methodaccording to claim 4, wherein communicating information between thedispenser device and the remote location comprises the dispenser deviceaccepting new dispensing instructions from the central data store. 6.The method according to claim 4, wherein communicating informationbetween the dispenser device and the remote location comprises providingsecure access to the stored information and instructions on the centraldata store to appropriate doctors and pharmacies via an internet serviceprovider.
 7. The method according to claim 1, wherein alerting a patientthat a dose of medication is to be taken or an optional dose ofmedication is available to be taken comprises emitting at least one ofan audio or visual signal indicating that the dose of medication isready to be taken.
 8. The method according to claim 7, furthercomprising instructing the dispenser device that the signal has beenreceived through a response mechanism actuatable by the patient.
 9. Themethod according to claim 1, wherein the biometric identification devicecomprises at least one of a biometric identification device fingerprintsystem or a retina scan system.
 10. The method according to claim 1,further comprising instructing the dispenser device to transmit anemergency message to an appropriate emergency response facility uponactuation of emergency assistance mechanism.
 11. The method according toclaim 1, further comprising a disabling functionality of the dispenserdevice based upon a predetermined criteria.
 12. The method according toclaim 1, further comprising tracking data on a controller of thedispenser device, wherein the tracked data comprises the dosage,compliance notification data, dose history, patient data, patientcompliance schedule and biometric information.
 13. The method accordingto claim 12, further comprising communicating the tracked data from thedispenser device to a central data store that also comprises trackeddata from other dispenser devices and patients about dispensing ofmedication.
 14. The method according to claim 13, further comprisingproviding secure access to the tracked data on the central data store toat least one of appropriate doctors, pharmacies, or administrators viaan internet service provider.
 15. The method according to claim 14,wherein an administrator can access the tracked data from multipledispenser devices for analysis.
 16. A method for controlling dispensingof medication, the method comprising: (a) holding at least onemedication within a dispenser device; (b) alerting a patient that a doseof medication is to be taken or an optional dose of medication isavailable to be taken; (c) confirming identification of the patient; (d)dispensing a dose of medication for the patient from the dispenserdevice; (e) confirming removal of medication from dispenser device; and(f) providing a location determination device with the dispenser deviceto permit locating the dispenser device.
 17. The method according toclaim 16, wherein alerting a patient that a dose of medication is to betaken or an optional dose of medication is available to be takencomprises emitting at least one of an audio or visual signal indicatingthat the dose of medication is ready to be taken.
 18. The methodaccording to claim 16, further comprising locating the dispenser devicevia the location determination device upon notification of misplacementof the dispenser device.
 19. The method according to claim 16, furthercomprising communicating information between the dispenser device and aremote location about dispensing of the medication.
 20. The methodaccording to claim 19, wherein the remote location comprises a centraldata store and communicating information between the dispenser deviceand the remote location comprises reporting status of the dispenserdevice to the central data store.
 21. The method according to claim 20,wherein communicating information between the dispenser device and theremote location comprises the dispenser device accepting new dispensinginstructions from the central data store.
 22. The method according toclaim 20, wherein communicating information between the dispenser deviceand the remote location comprises providing secure access to the storedinformation and instructions on the central data store to appropriatedoctors and pharmacies via an internet service provider.
 23. The methodaccording to claim 16, wherein confirming identification of the patientcomprises verifying the identity of the patient through a biometricidentification device.
 24. The method according to claim 23, wherein thebiometric identification device comprises at least one of a biometricidentification device fingerprint system or a retina scan system. 25.The method according to claim 23, further comprising tracking data on acontroller of the dispenser device, wherein the data tracked comprisesthe dosage, compliance notification data, dose history, patient data,patient compliance schedule and biometric information.
 26. The methodaccording to claim 25, further comprising communicating the tracked datafrom the dispenser device to a central data store that also comprisestracked data from other dispenser devices and patients about dispensingof medication.
 27. The method according to claim 26, further comprisingproviding secure access to the tracked data on the central data store toat least one of appropriate doctors, pharmacies, or administrators viaan internet service provider.
 28. The method according to claim 27,wherein an administrator can access the tracked data from multipledispenser devices for analysis.
 29. The method according to claim 16,further comprising instructing the dispenser device to transmit anemergency message to an appropriate emergency response facility uponactuation of emergency assistance mechanism.
 30. The method according toclaim 16, further comprising the disabling functionality of thedispenser device based upon a predetermined criteria.